NetObjects Fusion 7

home *** CD-ROM | disk | FTP | other *** search

/ NetObjects Fusion 7 / Fusion7.iso / NetObjects Fusion / data1.cab / Program_Executable_Files / NetObjects_System / JRE / 1.1 / README < prev

Wrap

Text File | 2002-10-18 | 25.1 KB | 609 lines

______________________________________________________________________ IBM Runtime Environment for Windows(R), Java(TM) Technology Edition, Version 1.1.7 Product README ______________________________________________________________________ The IBM Runtime Environment for Windows(R), Java(TM) Technology Edition, Version 1.1.7 (Runtime Environment) is based on Sun Microsystems' Java 1.1.7B maintenance level and provides the Sun Microsystems, Inc. Java Environment on: Windows 95 Windows 98 Windows NT 4.0 The Runtime Environment is provided as either: o A self-extracting InstallShield executable file (ibm-jre-n117p-win32-x86.exe) o A ZIP file (ibm-jre-n117p-win32-x86.zip). The IBM build number can be obtained by typing the following at a command line: jre -d ______________________________________________________________________ CONTENTS 1.0 BEFORE YOU INSTALL 1.1 Files Included with the Runtime Environment 1.2 The just-in-time (JIT) Compiler 1.3 Installation Considerations 1.4 Java Programs and "Native Method Interfaces" 2.0 UNATTENDED INSTALLATION 2.1 Uninstallation Language Considerations 3.0 REDISTRIBUTION REQUIREMENTS 3.1 Definition of Required and Optional Files 3.2 Files Required for Redistribution 3.3 Optional Files for Redistribution 4.0 THE JAVA RUNTIME INTERPRETER 5.0 EURO SYMBOL SUPPORT 5.1 Platform Support 5.2 Unicode Support 5.3 New Locales 5.4 Collation of Currency Symbols 5.5 Existing Java programs 6.0 RUNTIME EXAMPLE 7.0 RUNTIME DOCUMENTATION 8.0 GLOSSARY 9.0 TRADEMARKS 1.0 BEFORE YOU INSTALL ______________________________________________________________________ The Runtime Environment contains the required subset of classes to create a Java runtime environment and to run Java programs. It contains the Java Virtual Machine (JVM), Java core classes, and supporting files. The Runtime Environment does not contain all the classes found in the Java Developer Kit. 1.1 Files Included with the Runtime Environment ______________________________________________________________________ The Runtime Environment includes non-debuggable .dll or .so files plus classes from the Developer Kit software to support a program at runtime. The Runtime Environment does not include any of the development tools, such as appletviewer or javac, or classes that would pertain only to a development system. The Runtime Environment can be invoked from the command line by using the jre tool (see section, The Java Runtime Interpreter). On Windows platforms, the jre tool will ignore the CLASSPATH environment variable. Use the -cp option to specify an application's class path. The Runtime Environment generates a Java home directory using the location of the executable, but if the proper directory structure is not found, it refers to the registry to find the Java home directory. This allows for applications to embed the Runtime Environment within their directory structure and ensure that the Java home directory will always be resolved within the application directory. 1.2 The just-in-time (JIT) Compiler ______________________________________________________________________ The Runtime Environment includes the JIT compiler (ibmjitc.dll), which is enabled by default. To disable the JIT, pass the following -nojit option to the Runtime Environment at a command line: jre -nojit MyClass To verify whether or not the JIT is enabled, type the following at a command line: jre -d If a JIT is in use, the following message is displayed: compiler = enabled: ibmjitc If no JIT is in use, the following message is displayed: compiler = disabled The Runtime Environment also uses the java.compiler property to determine JIT usage and ignores the JAVA_COMPILER environment variable. 1.3 Installation Considerations ______________________________________________________________________ The self-extracting InstallShield executable file version copies jre.exe and jrew.exe into the Windows directory (Win95/98 = C:\Windows; NT 4.0 = C:\WINNT). If a version of jre.exe or jrew.exe currently exists in the Windows directory, you are prompted to overwrite the existing version with the current version. Installing these files into the Windows directory makes this Runtime Environment the default Java for the system. 1.4 Java Programs and "Native Method Interfaces" ______________________________________________________________________ Java programs that use the "native method interface" originally defined in Sun's JDK 1.0, are only supported by the IBM Runtime Environment when they are compiled by the IBM Win32 Developer Kit. Java programs that use the Sun recommended way of calling native code, Java Native Interface (JNI), introduced in Sun's JDK 1.1, are supported by the IBM Runtime Environment. 2.0 UNATTENDED INSTALLATION ______________________________________________________________________ To complete an unattended installation, you must first create a response file (setup.iss) that records the choices made during installation. (This is known as an interactive installation.) To create a response file while running the installation, type the following at a command line: ibm-jre-n117p-win32-x86.exe -r -fc:\temp\english\setup.ins Note: There are no spaces after -f, and c:\temp is the directory defined by the system's TEMP environment variable. To determine the directory of the TEMP environment variable, type SET at a command line. A response file will be created in the Windows directory. Depending on the platform you are using, the response file (setup.iss) will be created in the following directory: o Windows 95/98 X:\WINDOWS o Windows NT X:\WINNT Where X: is the boot drive. Note: If the following message occurs during an interactive installation, Another Java Runtime Environment is currently installed as the System JVM. Select Yes to overwrite this version or No to exit this installation. Select No and exit from the installation. Go to the Windows system directory and delete the following two files: o jre.exe o jrew.exe After you have deleted the files, restart the interactive installation using the command listed at the beginning of this section. Once you have created the response file, you can run an unattended installation by typing the following at a command line: ibm-jre-n117p-win32-x86.exe -s -fc:\temp\english\setup.ins -f1c:\setup.iss -f2c:\setup.log Note: There are no spaces after -f, -f1, or -f2. The -f1 flag specifies the name and location of the response file. The -f2 flag specifies the name and location of the log file. If the installation is successful, the log file will contain "ResultCode=0" 2.1 Uninstallation Language Considerations _______________________________________________________________________ The uninstall for an unattended installation is done by using the "Add/Remove Programs" icon in the control panel. The language used during uninstallation is the same as the language chosen during installation. (See example in section, Unattended Installation.) If you prefer a different language for uninstallation, the following languages are available: Simplified Chinese c:\temp\chi_simp Traditional Chinese c:\temp\chi_trad French c:\temp\french German c:\temp\german Italian c:\temp\italian Japanese c:\temp\japanese Korean c:\temp\korean Brazilian Portuguese c:\temp\portbrzl Spanish c:\temp\spanish Swedish c:\temp\swedish To use one of the above languages during uninstall, replace the language variable in the specified path. Where c:\temp is the directory defined by the system's TEMP environment variable. 3.0 REDISTRIBUTION REQUIREMENTS ______________________________________________________________________ The following sections describe the redistribution requirements. 3.1 Definition of Required and Optional Files ______________________________________________________________________ The files that make up the Runtime Environment are divided into two categories, required and optional. The files that are marked "optional" in this README do not need to be included in the redistribution of the Win32 JRE with the licensee's program. Most of the optional files provide localization support for languages. The term "required" means licensees that distribute the runtime must include those files with their program, whether or not their program ever uses those files. Those files are a required part of the Java platform. The Runtime Environment includes the bin and lib directories and both must reside in the same directory. This directory is <runtime-dir>. In the following lists, all paths are relative to the <runtime-dir> directory (which is originally jre1.1). 3.2 Files Required for Redistribution ______________________________________________________________________ The Win32 bin directory contains these executable files and native libraries: bin\jre.exe Java runtime executable file bin\jrew.exe Java runtime executable file, no console window bin\rmiregistry.exe rmiregistry executable file bin\javai.dll Java runtime native code library bin\JdbcOdbc.dll native code support for sun.jdbc bin\jpeg.dll native code support for sun.jpeg bin\math.dll native code support for java.math bin\mmedia.dll native code support for sun.audio bin\net.dll native code support for java.net bin\sysresource.dll native code support for sun.net.www.protocol bin\winawt.dll native code support for sun.awt bin\zip.dll native code support for java.util.zip bin\ibmjitc.dll IBM JIT compiler Note: The native code C runtime library, msvcrt.dll, is located in the Windows system directory. The location of this directory varies on different operating systems, but is usually: o Windows 95: windows\system o Windows 98: windows98\system o Windows NT: winnt\system32 The Win32 lib directory contains the classes and property files: lib\rt.jar Java runtime core classes lib\content-types.properties MIME-type properties lib\awt.properties properties for key events for java.awt lib\font.properties Win32 font properties for java.awt lib\serialver.properties serialization properties lib\security\java.security properties for java.security 3.3 Optional Files for Redistribution ______________________________________________________________________ The following files are optional: bin\javakey.exe javakey executable lib\i18n.jar I18N character conversion classes from sun.io lib\font.properties.ar AWT font properties for Arabic locale lib\font.properties.be AWT font properties for Byelorussian locale lib\font.properties.bg AWT font properties for Bulgarian locale lib\font.properties.cs AWT font properties for Czech locale lib\font.properties.el AWT font properties for Greek locale lib\font.properties.et AWT font properties for Estonian locale lib\font.properties.hr AWT font properties for Croatian locale lib\font.properties.hu AWT font properties for Hungarian locale lib\font.properties.iw AWT font properties for Hebrew locale lib\font.properties.ja AWT font properties for Japanese locale lib\font.properties.ko AWT font properties for Korean locale lib\font.properties.lt AWT font properties for Lithuanian locale lib\font.properties.lv AWT font properties for Latvian locale lib\font.properties.mk AWT font properties for Macedonian locale lib\font.properties.pl AWT font properties for Polish locale lib\font.properties.ro AWT font properties for Romanian locale lib\font.properties.s2 AWT font properties for Serb locale lib\font.properties.sk AWT font properties for Slovak locale lib\font.properties.sl AWT font properties for Slovene locale lib\font.properties.ru AWT font properties for Russian locale lib\font.properties.th AWT font properties for Thai locale lib\font.properties.tr AWT font properties for Turkish locale lib\font.properties.uk AWT font properties for Ukrainian locale lib\font.properties.yu AWT font properties for Serbo-Croatian locale lib\font.properties.zh_TW AWT font properties for Traditional Chinese locale lib\font.properties.zh AWT font properties for Simplified Chinese locale 4.0 THE JAVA RUNTIME INTERPRETER ______________________________________________________________________ The jre tool invokes the Java Runtime Interpreter for executing Java applications. The syntax for the jre command is: jre [ options ] classname <args> The classname argument is the name of the class file to be executed. Any arguments to be passed to the class must be placed after the classname on the command line. An alternative version of the tool, jrew, is available for Win32. The jrew command is identical to jre, except that a console window is not invoked. The syntax of the jrew command is jrew [ options ] classname <args> The Runtime Environment tool will ignore the CLASSPATH environment variable. Use the -cp option to specify an application's class path. Options for the jre and the jrew commands are as follows: -classpath path Specifies the path that jre uses to look up classes. Overrides the default classpath. -cp path Prepends the specified path to the default classpath that jre uses to look up classes. -help Print a usage message. -mx x Sets the maximum size of the memory allocation pool (the garbage collected heap) to x. The default is 16 megabytes of memory. x must be greater than or equal to 1000 bytes. -ms x Sets the startup size of the memory allocation pool (the garbage collected heap) to x. The default is 1 megabyte of memory. x must be greater than 1000 bytes. -noasyncgc Turns off asynchronous garbage collection. When activated, no garbage collection takes place unless it is explicitly called or the program runs out of memory. -noclassgc Turns off garbage collection of Java classes. By default, the Java interpreter reclaims space for unused Java classes during garbage collection. -nojit Do not invoke the just-in-time bytecode compiler. The virtual machine directly interprets bytecodes, without converting them to native code. -ss x The -ss option sets the maximum stack size that can be used by C code in a thread to x. The default units for x are bytes. The value of x must be greater than or equal to 1000 bytes. -oss x The -oss option sets the maximum stack size that can be used by Java code in a thread to x. The default units for x are bytes. The value of x must be greater than or equal to 1000 bytes. -v, verbose Causes jre to print a message to stdout each time a class file is loaded. -verify Performs byte-code verification on the class file. However, java -verify does not perform a full verification in all situations. Any code path that is not actually executed by the interpreter is not verified. Therefore, java -verify cannot be relied upon to certify class files unless all code paths in the class file are actually run. -verifyremote Runs the verifier on all code that is loaded into the system by a classloader. verifyremote is the default for the interpreter. -noverify Turns verification off. -verbosegc Causes the garbage collector to print out messages whenever it frees memory. -DpropName=value Defines a property value. propName is the name of the property whose value you want to change and value is the value to change it to. For example, the command java -Dawt.button.color=green ... sets the value of the property awt.button.color to "green." 5.0 EURO SYMBOL SUPPORT ______________________________________________________________________ The following sections describe euro symbol support with the Runtime Environment. 5.1 Platform Support ______________________________________________________________________ In order to take advantage of the euro symbol support, the operating system must support the euro symbol. Microsoft's support is as follows: Windows 95 Microsoft has posted a 'Windows 95 beta 1 euro product update' on their Web site. This update includes fonts and keyboard drivers. Windows 98 Contains codepage support for the euro, appropriate fonts and keyboard drivers. Windows NT 4.0 Microsoft has posted a 'Windows NT 4.0 euro product update' on its Web site. This update includes codepage support, fonts and keyboard drivers. It is also included in Service Pack 4, which can be found at the following Web site: http://www.microsoft.com/support/winnt/default.htm The encoded Windows core fonts that contain euro support are Times New Roman, Courier New and Arial. If you need to change your keyboard layout or input locale (see Regional Settings or Keyboard on the Control Panel), you should do this before installing the appropriate euro product update. The Microsoft Euro Currency Symbol FAQ Web page details the keyboard layouts that support the euro. If your input locale is EN English (United States), use US-International rather than US as the keyboard layout. You can then use the key combination right 'ALT' key and 5 to enter a euro character. The Windows code pages that include or will include the euro are: 1250 Central/Eastern European 1251 Cyrillic 1252 Western Europe 1253 Greek 1254 Turkish 1255 Hebrew 1256 Arabic 1257 Baltic 1258 Vietnamese 874 Thai The codepage converters for the codepages listed above have been modified to support the euro symbol. A number of additional codepage converters have been included to support the euro on IBM codepages, including those for EBCDIC. A new ISO codepage, ISO8859_15, has also been added. Note: The default converter for Western Europe locales has been changed from 8859_1 to Cp1252 as Cp1252 supports the euro and 8859_1 does not. Further information about operating system support for the euro may be added to the Microsoft Web site. 5.2 Unicode Support ______________________________________________________________________ The Unicode character for the euro is u'20ac'. 5.3 New Locales ______________________________________________________________________ A number of new 'ResourceBundle's have been created to support the euro. These are: LocaleElements_de_AT_EURO LocaleElements_de_DE_EURO LocaleElements_de_LU LocaleElements_de_LU_EURO LocaleElements_en_IE_EURO LocaleElements_es_ES_EURO LocaleElements_fi_FI_EURO LocaleElements_fr_BE_EURO LocaleElements_fr_FR_EURO LocaleElements_fr_LU LocaleElements_fr_LU_EURO LocaleElements_it_IT_EURO LocaleElements_nl_BE_EURO LocaleElements_nl_NL_EURO LocaleElements_pt_PT_EURO The method java.util.Locale.getDisplayVariant() has been modified to lookup the localized name of the euro locale (in all cases, "Euro") from the resource data. 5.4 Collation of Currency Symbols ______________________________________________________________________ Collation of currency symbols traditionally follows the English collation order of the symbol name. Thus 'cent' is followed by 'dollar.' According to this scheme, the euro symbol will sort immediately following the dollar and dong currency symbols and before the French franc. 5.5 Existing Java programs ______________________________________________________________________ Existing Java programs that support the euro symbol will run as before, with the exception of changes brought about by any new or altered default codeset converters. Programs can use the following code to get a locale that uses the euro from one that does not. Note: This code will only work for those locales that support the euro. if (source.getVariant().indexOf("EURO") >= 0) newLocale = source; else newLocale = new Locale(source.getLanguage(), source.getCountry(), source.getVariant().length()>0 ? (source.getVariant() + "_EURO") : "EURO"); 6.0 RUNTIME EXAMPLE ______________________________________________________________________ The following Sun Web page has a "Hello World" example that you can download. The example demonstrates how to create a simple Java application that runs on and is bundled with the Java Runtime Environment. You can find the example at: http://java.sun.com/products/jdk/1.1/jre/example/ The example shows how to make a simple, seamless transition from developing an application with a Developer Kit, to deploying it with the more lightweight Runtime Environment. 7.0 RUNTIME DOCUMENTATION ______________________________________________________________________ Runtime documentation is any documentation that end users might need after they have installed a Java program that runs on the Runtime Environment. IBM supplies the following runtime documentation: o Each property file contains comments that describe what the file is useful for and how to modify it. o awt.properties file - KeyEvent uses it to print out properties of key events, usually for debugging purposes. This might be used by an individual who is debugging an application and needs to print out events. 8.0 GLOSSARY ______________________________________________________________________ MIME An industry standard character encoding. Bytecode Compiled Java code. Garbage Collected Heap A heap that is asynchronously freed when not in use. <args> An industry standard way of describing inputs such as command line arguments or parameters to an API (application program interface). 9.0 TRADEMARKS ______________________________________________________________________ IBM is a trademark of International Business Machines Corporation in the U.S., or other countries, or both: The JRE is a product of Sun Microsystems, Inc. JavaSoft is an operating company of Sun, and develops the JRE. Java and HotJava are trademarks of Sun Microsystems, Inc. in the U.S. and other countries. The Java technology is owned and exclusively licensed by Sun Microsystems, Inc. Other company, product, and service names may be trademarks or service marks of others. THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. ______________________________________________________________________ (c) Copyright IBM Corporation 1999, All rights reserved. (c) Copyright ⌐ 1997, 1999 Sun Microsystems, Inc. 901 San Antonio Rd., Palo Alto, CA 94303 USA. All rights reserved.